home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 26
/
Cream of the Crop 26.iso
/
bbs
/
tftp156.zip
/
TOSSFTP.DOC
< prev
next >
Wrap
Text File
|
1997-06-20
|
12KB
|
257 lines
TOSS'in for FTP'in
Copyright(c) 1997, by Lyn B. Borchert
All Rights Reserved Internationally
[ Release v1.56 06/21/1997 ]
Please read this entire document before using TOSSFTP.
Author Contact Info has Changed!
LICENSE AND DISCLAIMER
"TOSSFTP" refers to all executables and documentation as distributed in the
compressed file in which this file was contained when released. For the
purposes of this document, "TOSSFTP" refers to the entire release package.
* TOSSFTP is copyrighted material by Lyn B. Borchert. It may only be
used in agreement with the conditions set out in this license
agreement.
* TOSSFTP is released under the shareware (try before you buy) concept.
- You may use TOSSFTP for an evaluation period of 30 days. After
this period you MUST either register TOSSFTP or stop using it and
delete any of the files associated with it other than the
distributed compressed file form.
- Registration is REQUIRED for commercial usage. (a commercial
environment is; a business, governmental organization,
association, school, foundation, or any other form of juridical
person, or any system where TOSSFTP is directly or indirectly used
to make profit).
- Each Registration is valid for only one instance of the program.
Each additional instance used must be registered separately.
Hence, Multiple processing systems where TOSSFTP is run under more
than one process must register each process where TOSSFTP is used.
- TOSSFTP may be distributed freely provided no money or any other
compensation is asked or accepted without prior written permission
from the author. CD-ROM makers and BBS sysops my distribute
TOSSFTP along with other shareware programs for the minor fee they
typically charge.
- TOSSFTP may not be incorporated into any other products'
distribution file or disks without prior written approval from the
author of TOSSFTP. Except where several other shareware programs
are being freely provided in exchange for duplicating and shipping
costs and where it is made known to the recipient that they are
not purchasing the TOSSFTP product and that registration of
TOSSFTP is still their obligation.
* Although care has been taken to write and test a program that does
what this document states, TOSSFTP is provided as is, without
warranty or guarantee of any kind, either expressed or implied, as to
the fitness for a particular purpose or quality or performance of
this program, except that TOSSFTP will occupy disk space.
* In no event shall Lyn B. Borchert be liable to you or anyone else for
any damages or cost, including, but not limited to, any lost profits,
lost savings or lost income which may have resulted from the use or
inability to use TOSSFTP.
* In no way is Lyn B. Borchert obligated to you or anyone else to
provide future versions of, or support for TOSSFTP.
* Lyn B. Borchert reserves the right not to release future shareware
versions of TOSSFTP, but switch to a commercial "buy before you try"
marketing concept instead.
* If you are currently using an unregistered version of TOSSFTP, then
you are asked to make a small advertisement for TOSSFTP, in the inlog
procedure for your BBS system.
* The compressed file containing the TOSSFTP package may be
re-compressed using a different program provided all files are
included in the new compressed form.
* Distributors are not given permission to include any additional files
with the TOSSFTP package.
* Registered versions of TOSSFTP are non-transferable. You may not
sell or give your serial number to someone else. All serial numbers
and the rights to use a serial number are kept by Lyn B. Borchert.
* Disassembling or HEX editing of the Executable file(s) is expressly
forbidden. Doing so is a direct violation of this license agreement.
* Registration does not obligate Lyn B. Borchert to support this
product. Registration only grants you the privledge of using this
version of the TOSSFTP package.
* Your use of TOSSFTP constitutes your agreement to this license and
disclaimer and your release of the author from any form of liability
or litigation.
REGISTRATION
After 30 days of evaluation use, you are required to register the TOSSFTP
package if you intend to continue using it.
Single non-commercial instances of use can be Registered for $10.00 each use.
Multiple non-commercial instances of 5 or more can be Registered for $40.00
per each group of 5.
Single Commercial instances of use can be Registered for $20.00 each use.
Multiple Commercial instances of 5 or more can be Registered for $80.00
for each group of 5.
To register, you must fill out the included registration form and mail it
to the indicated address along with the required funds. (TOSSFTP.REG)
All serial numbers will be delivered via U.S. Mail. In addition, if you
request it on the form, your serial number can also be sent to you via
Internet E-mail or can be placed on hold for your FidoNet Mailer to
retreive from my BBS.
Sorry, but at this time, online registration via credit card is not
available.
Failure to register will cause the program to delay at start up and again
when it finishes processing. It will also make some noise during these
delays. The delays will start 30 days after the program is first run, so
for the evaluation period there should be no annoyances and all features
will work. Even after the evaluation period all features will work, the
program is not crippled! It is annoying after 30 days though.
QUIK DOCs
There's not much to it. Place TOSSFTP.EXE and TOSSFTP.CFG in the same
directory. Edit the config file to match your system. Then just before
you are going to start the process to transfer mail to your uplink via FTP,
run TOSSFTP from the sub-directory that it resides in. (I put mine in my
echomail tosser directory)
WHAT THE HECK DOES IT DO?
Well first I should explain how getting your mail via FTP works. (for me
anyway) Basically, there is an FTP host that packages all my echomail in
the normal FidoNet compressed mail format so I can call in and transfer it
to my host. I then download it from my host to my computer and toss it
the same as if I had just finished receiving it through the phone lines.
I can deliver outgoing mail by uploading it and leaving it at the FTP host.
The problem there is it must be in FIDO(tm) compressed form (*.pkt) for him
to process it. As all of us who run Fido Style Mailers know, netmail is not
in compressed format on our systems. It sits in our mail directory as
*.msg files. The FTP host can't do anything with *.msg files.
As a result, I would have to send my AREAFIX and File Echo link request
messages via telephone. So, I wrote TOSS'in for FTP'in to scan my mail
directory looking for these link messages and compressing them into Fido
Style *.PKT files. That way they could be uploaded with the rest of the
outgoing compressed mail and the FTP host could process them. Thus
eliminating the need to call long distance to deliver Areafix messages.
While I was at it (scanning the mail directory that is), I figured I might
as well copy the outbound compressed mail to a temporary directory also.
After all, there were messages there that are file attachs of the outgoing
mail and once the mail is gone, those messages needed to be deleted and the
compressed files truncated. All stuff I was doing manually before.
TOSSFTP will also pack up any routed netmail messages to be delivered on up
the line as well. The TOSSFTP.CFG files and history file will give you
specific information on how to specify what gets tossed and what doesn't.
So, that's pretty much what TOSSFTP does. To be more specific and concise...
When TOSSFTP is run, it first reads in the config file.
Then it reads in each *.msg file in the mail directory.
It looks at each message header to see if this message is destine for my
uplink by comparing the destination Net/Node number in the message header
with what I put in the config file.
If a match is found, it then checks the TO: field of the message to see if
either the AREAFIX name or FILEFIX name is there.
If it is, then TOSSFTP makes a *.PKT out of that entire message and places
it in the OUTBOUND directory and deletes the *.msg.
If not, it takes a look at the subject line and checks to see if the path
to my PACKETS directory is in there.
If it is, that means this is a file attach message for an outgoing mail
bundle which is named in the subject line. TOSSFTP then copies the
compressed bundle from the PACKETS directory to the OUTBOUND directory,
then truncates the original and deletes the *.msg. Just like your mailer
would do if it had just finished delivering this mail via the phone line.
[NOTE: TOSSFTP will never toss a File Attach message that is not an
Echomail Bundle. Host Routing File Attach messages is against the rules.]
At this point, I would execute my script file to call my InterNet provider,
log in, upload all the files in the OUTBOUND directory, then (provided the
transfer was a success) it deletes all the files in my OUTBOUND directory
and proceeds to FTP the outgoing mail to my FTP host and retrieve my
incoming mail from the FTP host. Then I download the incoming files into
my Inbound directory, (again, if the transfer was a success) it deletes the
incoming mail from my Internet provider's drive and logs off the Internet.
Next the batch file runs my mail tosser and finally reloads my mailer.
That's about all there is to it.
THE FUTURE.
The work I do on TOSSFTP is directly related to my personal needs first and
secondly to the needs of registered users. The more registered users there
are the more I will feel the desire to work on the program. There is lots
that can be done to improve and enhance TOSSFTP and I suspect I will
continue to make those changes over time.
I'm always open to suggestions for enhancements and improvements. Several
very good suggestions have come from registered users. Some were even
things I would have never thought of, so don't be shy with your
suggestions.
CONTACTING THE AUTHOR
(all this information is subject to change over time)
Snail Mail:
Lyn Borchert
4956 E. 3rd Street
Tucson, Arizona 85711
FidoNet Mail:
1:300/12@FIDONET
InterNet e-Mail:
lyn.borchert@usa.net
BBS Number:
(520) 326-2999
Web Site:
http://www.dakotacom.net/~lynbor
My Voice Phone number was intentionally left out. Please do not call me
voice to talk about TOSSFTP. I read my mail every day and most of the time
more than once a day. Mail reading I can do when it is convient to me.
Voice messages from non-registered users will be totally ignored and those
from registered users will be annoying to me, so please don't call me voice.